Policies and roles

A role is a single permission. livehub/alarms/read, for example, permits viewing alarms. Roles are written as a path, and a * at the end means everything under it: livehub/bots/* covers reading, creating, editing, and deleting bot connections, while livehub/bots/read covers only the first.

A policy is a named set of roles. Configuration Viewer, for instance, gathers the read-only role for every configuration screen into a single policy you can assign.

A user group carries policies, and a user in that group has every role in them. The chain runs user → group → policy → role.

Live Hub supplies the policies, and they cannot be edited or deleted. You choose which policies a group carries and who is in the group.

For the full list, see Predefined policies.